A competent SMPTE ST 2110 technician needs a solid, practical understanding of the Ethernet / Data-Link layer (OSI Layer 2), because nearly all modern 2110 deployments run over standard Ethernet infrastructure.
While many day-to-day tasks are handled by switches and NICs automatically, a good 2110 tech must know enough to design, troubleshoot, and explain why the network behaves the way it does—especially when things go wrong. Here are the key concepts every competent 2110 tech should know well:
| Topic | What a competent 2110 tech should know | Why it matters in ST 2110 deployments |
|---|---|---|
| Ethernet frame structure | Preamble + SFD (8 bytes, PHY), Destination/Source MAC (12 bytes), EtherType (2 bytes), Payload (46–1500 bytes), FCS (4 bytes) → total 1518 bytes max (excluding PHY bytes) | You must understand why jumbo frames (MTU >1500) are almost always required for efficient uncompressed video transport |
| MTU and Jumbo Frames | Standard MTU = 1500 bytes; most 2110 facilities use 9000-byte jumbo frames (or at least 4000–8000) | Uncompressed HD ≈ 3 Gbps, 4K ≈ 10–12 Gbps → small MTU causes excessive packetization overhead and higher CPU/NIC interrupt load |
| MAC addressing & multicast | 48-bit MAC addresses; multicast MACs begin with 01:00:5E (IPv4) or 33:33 (IPv6) | ST 2110 uses IP multicast for essence distribution; switches must support IGMP snooping to avoid flooding multicast traffic |
| IGMP Snooping & Querier | Layer 2 switches must have IGMP snooping enabled; there must be an active IGMP querier on the network | Without this, multicast streams flood every port → bandwidth waste and potential switch CPU overload |
| Collision domains | In modern switched full-duplex Ethernet, each port is its own collision domain (no collisions) | Half-duplex/shared media is obsolete and unacceptable for 2110 (increases jitter and loss risk) |
| VLANs & tagging (802.1Q) | 4-byte 802.1Q tag inserted after source MAC; VLAN ID is 12 bits (1–4094) | Most 2110 facilities use separate VLANs for red/blue networks (ST 2022-7), PTP, management, etc. |
| VLAN tagging vs untagged ports | Access ports (untagged), trunk ports (tagged + possibly native VLAN), voice VLAN, etc. | Misconfigured trunk vs access port is a common reason 2110 streams disappear |
| Spanning Tree Protocol (STP/RSTP/MSTP) | Prevents loops; elects root bridge; blocks redundant links; convergence time (RSTP ~seconds) | Loops still happen in large facilities → broadcast storms can kill 2110 streams quickly |
| Link Aggregation (LACP/802.3ad) | Bundles multiple physical links into one logical link; load-balancing based on a hash (MAC, IP, ports) | Common for high-bandwidth server NICs and inter-switch links; wrong hash algorithm can create uneven load |
| Flow control (802.3x) | Pause frames when receive buffer is full; can be dangerous in multicast environments | Many 2110 vendors recommend disabling flow control to prevent head-of-line blocking |
| QoS at Layer 2 (802.1p / PCP) | 3-bit priority field in VLAN tag (0–7) | Some facilities use PCP to prioritize PTP and audio over video; less common than DSCP but good to know |
| EtherType values | 0x0800 = IPv4, 0x86DD = IPv6, 0x8100 = 802.1Q VLAN tag | Fast way to confirm whether traffic is properly tagged or encapsulated |
| Maximum frame size & baby giants | Frames <64 bytes are runts; >1518 (or jumbo limit) are giants | “Baby giants” often indicate VLAN tag mishandling (e.g., double-tagging or missing tag stripping) |
| Port mirroring / SPAN | Copies traffic from one or more ports to a monitor port | Essential troubleshooting tool for capturing 2110 streams with Wireshark |
| Broadcast / multicast storm protection | Storm control / rate limiting on switch ports | Protects against accidental loops or faulty devices flooding the network |
Quick "Competency Checklist" for a 2110 Tech
A strong 2110 technician should be able to:
You don't need to be a CCNP-level switching expert, but you must understand Layer 2 well enough to diagnose 80% of the network-related problems that break 2110 streams in real facilities.
